Skip to content

Change log level from warn to debug for successfully created missing …#648

Closed
TheDGOfficial wants to merge 2 commits intoembeddedt:26.1from
TheDGOfficial:patch-2
Closed

Change log level from warn to debug for successfully created missing …#648
TheDGOfficial wants to merge 2 commits intoembeddedt:26.1from
TheDGOfficial:patch-2

Conversation

@TheDGOfficial
Copy link
Copy Markdown
Contributor

…block entities

This message spams the logs in Hypixel. The else case already logs at error level; so logging it for the successful case would only bury the error case in the logs. I feel like debug log level would be apporiate here, which won't be logged by default at least on Fabric. I'm not sure if Forge still enables debug log level by default, please let me know.

…block entities

This message spams the logs in Hypixel. The else case already logs at error level; so logging it for the successful case would only bury the error case in the logs. I feel like debug log level would be apporiate here, which won't be logged by default at least on Fabric. I'm not sure if Forge still enables debug log level by default, please let me know.
Slightly more performant if debug logging not enabled. Could also use a Supplier taking overload of the .debug method, but that incurs additional lambda object creation that would most likely neglect any performance gains from not evaluating the toShortString method.
@embeddedt
Copy link
Copy Markdown
Owner

Seems reasonable. Will apply this to the 1.20 branch manually (it gets propagated upwards from there as mentioned in CONTRIBUTING.md).

Out of curiosity, what Hypixel gamemode has enough block entities for this to be an issue?

@embeddedt embeddedt closed this in 26bd711 Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants